cm.VSM.DropReplySeqNumMismatch

Description

Configuration reply to the application was dropped. Reason provided : Meaning "sequence number mismatch" : Local client is processing a request with different sequence number 1. If Current # > Received # sequence number, then probable cause would be connection issue. 2. If Received # > Current # sequence number, then internal condition related to software. "no outstanding request" : Local client does not have any request pending.

Remedy

This is a rare condition which may be related to software, and may require a reboot to correct the problem. If it persists, contact technical support and provide outputs of 'show switch', 'show log'.

Severity

Error

Message Text

Dropped (%msgType%) reply to request number %seqNum% handled by client %client% due to %reason%.

Message Parameters

Name Type
seqNum uInt32
client String
reason String
msgType String